UCT/CUDA_COPY: Fix incorrect mem_flags detection - v1.22.x#11645
Merged
brminich merged 3 commits intoJul 10, 2026
Conversation
tomerg-nvidia
changed the title
tvegas1
approved these changes
Jul 10, 2026
brminich
approved these changes
Jul 10, 2026
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
4 participants
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
What?
Push a cuda context before flag detection if the flag detection is going to export dmabuf fd.
If Memory is host-based vmm, skip the dmabuf fd check and just mark as registerable.
Why?
If there's currently no context and the memory flags detection is called the dmabuf export can fail, making it non-registerable.
Host-based vmm fail dmabuf fd export.
How?
Push context when needed, trying to use available context first
Backport of #11635
Contains also #11642